Add agent-feedback setup and take over the streaming render gap - #34
Conversation
|
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #34 +/- ##
=======================================
Coverage 65.42% 65.42%
=======================================
Files 3 3
Lines 188 188
Branches 50 50
=======================================
Hits 123 123
Misses 44 44
Partials 21 21 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
1 participant
Sets up
agent-feedback/the way the other marko-js repos have it, plus a minimalAGENTS.mdpointing at it (this repo had none).The first entry was found while working in marko-js/marko:
render()doesString(await template.render(input)), which drains the Marko 6 stream to completion, so a server test can never observe an<await>/<try>placeholder and an unsettledload()hangs until timeout. Nothing is needed from marko —pipe(),toReadable()and[Symbol.asyncIterator]()already exist there.Removed from marko in marko-js/marko#3714.